Skip to content

Use compatPatrouille #410

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
May 25, 2025
Merged

Use compatPatrouille #410

merged 1 commit into from
May 25, 2025

Conversation

mikepenz
Copy link
Owner

Description

  • use compatPatrouille

Type of change

Please delete options that are not relevant.

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to not work as expected)
  • Documentation update
  • Code style update (formatting, renaming)
  • Refactoring (no functional changes, no API changes)
  • Build configuration change
  • Other (please describe):

@mikepenz mikepenz requested a review from Copilot May 25, 2025 17:15
@mikepenz mikepenz added the other label May 25, 2025
Copy link
Contributor

@Copilot Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull Request Overview

Refactors project configuration to align with the updated compatPatrouille setup by bumping version catalogs, updating resource imports, and adjusting plugin ordering.

  • Upgraded the version-catalog dependency to 0.4.2
  • Switched the Web sample’s WASM instantiation import to use markdown.uninstantiated.mjs
  • Reordered plugins in the shared Gradle build script

Reviewed Changes

Copilot reviewed 4 out of 4 changed files in this pull request and generated no comments.

File Description
settings.gradle.kts Bumped version-catalog from 0.3.9 to 0.4.2
sample/web/src/commonMain/resources/load.mjs Changed import from aboutlibraries to markdown
sample/shared/build.gradle.kts Moved Kotlin Multiplatform plugin below Android
Comments suppressed due to low confidence (1)

sample/shared/build.gradle.kts:3

  • Reordering the Kotlin Multiplatform plugin after the Android Library plugin can lead to configuration issues, as KMP should be applied first to set up targets correctly. Consider restoring the original order or validating that multiplatform targets still resolve as expected.
id("com.mikepenz.convention.kotlin-multiplatform")

@mikepenz mikepenz merged commit f460cf6 into develop May 25, 2025
3 checks passed
@mikepenz mikepenz deleted the feature/compatPatrouille branch May 25, 2025 17:26
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant